Adopt proof-pr v0.2.1#96
Conversation
saagpatel
force-pushed
the
chore/proof-pr-v0.2.1
branch
from
bae3966 to
698b6fd
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bae39661af
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| receipt_path: proof-pr.json | ||
| proof_pr_ref: v0.2.0 | ||
| proof_pr_ref: v0.2.1 | ||
| check_public_git_metadata: true |
There was a problem hiding this comment.
When this manual workflow is dispatched on this PR branch, the v0.2.1 reusable workflow defaults public_git_metadata_ref to github.sha and runs proof-pr check-public-git-metadata --ref "$PUBLIC_METADATA_REF"; the CLI only allows GitHub noreply emails. The reviewed commit itself is authored and committed as Codex <codex@openai.com>, so setting check_public_git_metadata: true makes the new proof workflow fail before it can validate or upload the receipt for this change. Rewrite the commit metadata to an allowed noreply identity or defer the gate until the checked ref is clean.
Useful? React with 👍 / 👎.
1 participant
Summary
v0.2.1proof_pr_reftov0.2.1Proof Bundle
Risk:
T3Receipt:
proof-pr.v1for698b6fde9b8c1633ac303922ad3a008e7796abb3Decision:
ready_with_operator_awarenessEvidence:
v0.2.1release exists with validated receipt asset ->passed.v0.2.1->passed.not_applicable(legacy repo history is not noreply-clean yet; keep adoption advisory-only.)passed(manual workflow passed on PR Adopt proof-pr v0.2.1 #96.)documented(revert this PR or pin back tov0.2.0.)Known gaps: